Method of drafting control and instrumentation technology

ABSTRACT

A method of drafting a program code of control and instrumentation technology for operating a plant is disclosed using industrial components. The program code, in its graphical representation, comprises a plurality of sub-plans. The program code of the control and instrumentation technology and the industrial components are represented together in a machine-readable technology plan. The sub-plans, especially the functional plans of the individual plane, are automatically generated from the technology plan, and the individual sequences of the program code are generated from the functional plans. The method makes manual drafting or manual correction project planning superfluous.

This application is the national phase under 35 U.S.C. § 371 of PCTInternational Application No. PCT/DE00/03319 which has an Internationalfiling date of Sep. 22, 2000, which designated the United States ofAmerica, the entire contents of which are hereby incorporated byreference.

FIELD OF THE INVENTION

The present invention generally relates to a method for producing aprogram code for instrumentation and control for operating aninstallation with process-engineering components. Preferably, theprogram code includes a multiplicity of individual sequences.

BACKGROUND OF THE INVENTION

Process-engineering components such as pumps, valves, containers andmeasured-value pickups have to date been shown in a first diagram, andthe program code for instrumentation and control has been shown in asecond diagram. To improve clarity, these two diagrams have beencombined in a general diagram produced manually. The reason for this isthat such a general diagram is the only basis on which it is possiblefor the process-engineering operatives and the control operatives tocooperate.

In the graphical representation, the program code for instrumentationand control comprises a multiplicity of sub-diagrams, particularlyfunction diagrams for the individual level. These sub-diagrams are usedfor implementing the required process-engineering functions, such asregulation, partial or group control, step control and measurement andalso measured-value correction and the like. The individual sub-diagramshave corresponding software modules which are connected to one another.The sub-diagrams themselves are also linked to one another, for exampleby defined break points. The sub-diagrams are graphical representationsof the individual sequences of the program code.

The known general diagram is an exclusively graphical representation.Consistency and freedom from error have to be ensured manually. Changesin the program code for instrumentation and control or in theprocess-engineering components likewise have to be made manually. Themanagement of change is therefore complex and prone to error. Continualmatching of the program code or of the process-engineering components tochanges in the general diagram, or vice versa, is virtually impossible.

SUMMARY OF THE INVENTION

It is therefore an object of an embodiment of the present invention toprovide a method with which the production and maintenance of theindividual diagrams, particularly the configuration of change, areconsiderably simplified and/or sources of error are minimized orprecluded.

An embodiment of the invention which may achieve this object can includea method wherein information about the program code for instrumentationand control, the process-engineering components and their links is showntogether in at least one machine-readable technology diagram.Preferably, at least one technology diagram is used for automaticallygenerating subdiagrams, particularly function diagrams for theindividual level, which are a graphical representation of the individualsequences. Also, the individual sequences of the program code can beautomatically generated from the sub-diagrams.

Once the technology diagram has been produced, the sub-diagrams and theindividual sequences of the program code are produced automatically.Thus, manual implementation is no longer necessary. The errors whichhave arisen previously during implementation can thus be avoided. Thesub-diagrams can readily be tracked to changes in the technologydiagram. Thus, the configuration of change is simplified considerably.In addition, the relevant, current information is always available inthe technology diagram and is displayed there. The cooperation betweenthe process-engineering operatives and the control operatives issignificantly simplified.

Advantageously, the technology diagram is divided into a series ofsections. These sections structure the technology diagram and make iteasier to find particular positions. The structuring is particularlyuseful in the case of large technology diagrams and improves clarity.

In one advantageous refinement, precisely one sub-diagram is generatedfrom precisely one section. The bounds of the sub-diagrams can thus bestipulated in the technology diagram, and the scope of each sub-diagramis defined precisely. It is also possible to see which sub-diagramsexchange information with one another, so that signal configuration issimplified.

In accordance with one advantageous development, each section comprisesa series of symbols, and each of these symbols is assigned to preciselyone module of the associated sub-diagram. The number of modules in thesub-diagram thus corresponds to the number of symbols in the section ofthe technology diagram. In addition, standardized symbols for thetechnology diagram can be provided for the standardized modules of thesub-diagrams.

Advantageously, precisely one individual sequence of the program code isgenerated from each sub-diagram. The individual sequences can thereforebe checked quickly. In addition, the number of individual sequencesgenerated needs to correspond to the number of sub-diagrams, and henceto the number of sections in the technology diagram, so that a simpleplausibility check can be carried out.

In accordance with one advantageous refinement, to improve clarity, aplurality of symbols and/or a plurality of sections of the technologydiagram are combined and put together to form a diagram symbol. This iscalled “diagram in the diagram”. The diagram symbol is split into thefundamental symbols and/or sections by means of a suitable action. Thesesymbols and/or sections can then be checked directly in the technologydiagram and can be altered if appropriate. Naturally, a plurality oflevels of diagram symbols are possible. The diagram symbols improveclarity, since, by way of example, sections of the technology diagramwhich have already been processed can be put together in acharacteristic diagram symbol. This significantly simplifies thegraphical representation of the technology diagram, and informationwhich is not required at the present time is not shown.

Advantageously, symbols contained in the technology diagram are providedwith an identification. This identification is unique either across theinstallation or in relation to the technology diagram. It allows thesymbols to be clearly assigned to the modules of the sub-diagrams.

In one advantageous refinement, the technology diagram is subjected to aplausibility check. Errors arising during configuration are identifiedand can be immediately eliminated.

In accordance with one advantageous development, a consistency check iscarried out between the individual sub-diagrams and between thesub-diagrams and the technology diagram. The consistency check involvesthe identification of errors or gaps in the configuration, and acorresponding report is output.

Advantageously, the technology diagram is provided with at least oneinterface for connecting it to other engineering systems. This allowsinformation to be imported into the technology diagram from otherengineering systems. It is naturally also possible for information to beexported from the technology diagram to other engineering systems.Information which is already available can thus be imported into thetechnology diagram quickly, effortlessly and without transmissionerrors. In addition, individual parts of the technology diagram can beexported to other engineering systems for processing and, followingprocessing, can be imported into the technology diagram again.Furthermore, it is possible for information to be exchanged betweenincompatible engineering systems using the technology diagram.

In accordance with one advantageous refinement, information contained inthe technology diagram is shown graphically. To show this information,graphical symbols are advantageously imported into the technologydiagram. It is thus possible to use meaningful, self-explanatorysymbols. These symbols can be selected or produced and imported into thetechnology diagram by the operatives themselves. This significantlyimproves clarity.

In one advantageous development, only some of the information containedin the technology diagram is shown graphically. Overloading of thetechnology diagram with information which severely reduces the clarityis reliably avoided. A suitable action from a user calls and displaysthis information which is not shown graphically. This information canthen be checked and, if appropriate, altered and stored. When editing iscomplete, the display is closed again, so that the clarity of thetechnology diagram is restored.

Advantageously, only some of the information required for fullygenerating the sub-diagrams and individual sequences is included in thetechnology diagram. The sub-diagrams contain detailed information, suchas monitoring times, threshold values and similar variables which are inmany cases not yet definite at the time at which the technology diagramis produced. This information has no further relevance to the technologydiagram, since it relates only to details of the instrumentation andcontrol and does not affect the basic structure of the instrumentationand control. This information can frequently be input only when thebasic structure of the program code for instrumentation and control hasbeen stipulated. According to an embodiment of the invention, thetechnology diagram is therefore produced without this information, andthis information is added subsequently. It can be added either in thetechnology diagram or directly in the individual sub-diagrams orindividual sequences.

In accordance with one advantageous development, generation of thesub-diagrams involves the identification and display of gaps in theinformation contained in the technology diagram. This ensures that thesub-diagrams are generated and configured completely.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is explained in more detail below using exemplaryembodiments which are shown schematically in the drawings. The samereference symbols are used for elements which are the same or haveidentical functions in the drawings, in which:

FIG. 1 shows a schematic illustration of the inventive method in a firstembodiment;

FIG. 2 shows a schematic illustration of a technology diagram;

FIG. 3 shows an enlarged illustration of a section from the technologydiagram shown in FIG. 2;

FIG. 4 shows an illustration of a function diagram;

FIG. 5 shows the illustration of a step control function in thetechnology diagram;

FIG. 6 shows an enlarged illustration of an individual step from FIG. 5;

FIG. 7 shows a schematic illustration of the signal configuration;

FIG. 8 shows the hierarchical structure of the instrumentation andcontrol;

FIG. 9 shows an illustration of a report;

FIG. 10 shows a schematic illustration of the transfer of informationbetween technology diagram and Sub-diagram; and

FIG. 11 shows a schematic illustration of a second embodiment of theinventive method.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 shows a schematic illustration of the inventive method. Atechnology diagram 10 is provided which contains both a diagram 11 ofthe process engineering and a diagram 12 of a program code 52 forinstrumentation and control. The separation between the two diagrams 11,12 is indicated schematically by the dashed line 13.

The diagram 11 of the process engineering contains a series ofprocess-engineering components. FIG. 1 schematically shows a pipe 14, acontainer 15 and a valve 18. These components 14, 15, 18 form aninstallation.

The diagram 12 of the program code 52 is divided into a series ofsections 24, 25. The division is indicated by means of dash-dot lines.These sections 24, 25 each comprise one or more symbols 21 which arelinked to one another. The symbols 21 and their links schematicallyrepresent the program code 52 for instrumentation and control which isrequired for operating the installation.

According to an embodiment of the invention, the technology diagram 10is machine-readable. From a respective section 24, 25, a functiondiagram 27 is produced. This is shown schematically with reference tothe section 24.

The section 24 is first identified as a separate section of thetechnology diagram 10, as shown by arrow 38. Next, each symbol 21 a, 21b, 21 c of the section 24 is assigned precisely one module 32 a, 32 b,32 c of the associated function diagram 27. This is indicatedschematically by the arrows 39. The links between the individual symbols21 a, 21 b, 21 c are likewise transferred to the function diagram 27.The function diagram 27 can thus be automatically generated from thetechnology diagram 10.

From the function diagram 27, an individual sequence 53 of the programcode 52 is then generated, as shown by arrow 83. The modules 32 of thefunction diagram 27, their links and break points are automaticallyconverted into the corresponding instructions of the individual sequence53. From each function diagram 57, precisely one individual sequence 53is generated. The individual sequences 53 generated are put together inthe program code 52 as shown schematically by arrow 84.

FIGS. 2 to 4 schematically show a larger illustration of a furthertechnology diagram 10, of a further section 24 and of the associatedfunction diagram 27. The technology diagram 10 shown in FIG. 2schematically describes a regulation function for the water level in thecontainer 15. For this purpose, a level sensor 16 and two control valves17, 18 with associated individual control elements for servomotors 19,20 are provided. On the basis of the signal from the level sensor 16,the control valves 17, 18 and [lacuna] are operated by the servomotors19, 20. Water is supplied via a pump 49.

The diagram 12 of the program code 52 shown in FIG. 2 contains not onlythe section 24 but also a series of comparators 22 and diagram symbols23 and a unique identification 26. The diagram symbols 23 represent agraphically reduced representation of a plurality of symbols 21 and/orof a plurality of sections 24, 25. The information contained in thesesymbols 21 and sections 24, 25 is shown in no more detail in thetechnology diagram 10 shown in FIG. 2. This considerably facilitatesclarity.

To show the information contained in the diagram symbol 23 in detail,the operator performs a suitable action. Particularly in the case ofconfiguration directly on the screen, the detailed information can beshown by double clicking with the left-hand mouse button on therespective desired diagram symbol 23.

It is possible for a plurality of levels of such diagram symbols 23 tobe connected above one another. In addition, a whole section 25 can becondensed to form a single diagram symbol 23.

To show the symbols 21, comparators 22 and diagram symbols 23, it ispossible either to use existing graphical elements or to produceseparate graphical elements and import them into the technology diagram10.

The section 24 shown in FIG. 3 corresponds to the function diagram 27shown in FIG. 4. For the purpose of clear association, both the section24 and the function diagram 27 have been provided with an identification37, 31. The symbols 21 in the section 24 and the modules 32 in thefunction diagram 27 also have a corresponding identification 36, 65.

The function diagram 27 comprises a link region 28 in which theindividual modules 32 are shown and are connected to one another. It isalso provided with a table 29 for input signals 33 and with a table 30for output signals 34, 35. The identifications 31, 37 of the functiondiagram 27 and of the section 24 and the identifications 36, 65 of thesymbols 21 and of the modules 32 provide a clear association between thetechnology diagram 10 and the function diagram 27. The input signals 33and output signals 34, 35 are clearly stipulated by means of suitablebreak points.

The bounds of the sections 24, 25 in the actual technology diagram 10stipulate which signals are exchanged between the function diagrams 27.The number of these signals can be recorded and subsequently used for aplausibility and consistency check between the technology diagram 10 andthe function diagrams 27.

FIGS. 5 and 6 schematically show the technology diagram for a stepcontrol function. The step control function comprises three steps 40,41, 45 which are shown clearly. Any number of steps can be shown. Foreach step 40, references 42 with definitions of break points are shown.The transition T₁ denotes the passage between the steps 40 and 41. Thetransition condition comprises the link 43. This link can be assigned toa separate section 44. The link 43 is configured as a separate functiondiagram 27. Hence, a separate function diagram is produced for thedefined diagram sections. The logic structure can thus be as complex asdesired, and storing modules such as timers or flip-flops can also beused.

FIG. 6 gives an enlarged illustration of the macro-step 45. Themacro-step 45 comprises two steps 47, 48, to each of which acorresponding reference 42 is assigned. In the case of configuration onthe screen, the enlargement is called up by double clicking on step 45in FIG. 5. Following completion of the configuration of the macro-step45 in the technology diagram, the enlargement is closed again, so thatthe clear representation of FIG. 5 is produced.

In line with FIGS. 2 and 3, combinational logic functions such aspartial and group control or measured-value corrections are also shown.This is possible as a result of the automatic generation of the functiondiagrams 27 from the technology diagram 10. The overall control task canthus be recorded continuously in the technology diagram 10.

The associated signal configuration is shown schematically in FIG. 7.The left-hand half shows a first technology diagram 10, and theright-hand half shows a second technology diagram 10′. The technologydiagram 10 defines clear break points 51 for each diagram section 50.For the purpose of further characterization, an identification 26, 26′is also provided for each technology diagram 10, 10′. References to thedefined signals are formed from the identification 37 for the diagramsection 50 and from the signal name. In the technology diagram 10′, thesignals 51 which are formed in the technology diagram 10 and serve asbreak points are complemented and provided with a reference using thediagram name formed by means of 37′. The technology diagram 10′ itselflikewise has an identification 26′. A suitable action can be used tocall the original technology diagram 10 from the technology diagram 10′and to alter it if appropriate.

Connections between individual symbols 21 in the technology diagram 10which extend beyond the bounds of sections 24, 25 correspond tocross-diagram break points 50 in the function diagrams 27, such as alsoarise in the case of manual connection between two modules 32 indifferent function diagrams 27.

Naturally, a plurality of technology diagrams 10′ can again be puttogether to form a further technology diagram 10″. This produces thediagram symbols 23, which allow a clear representation.

FIG. 8 schematically shows the hierarchical structure of the programcode 52 for instrumentation and control which is used. Within aninstallation 60, any number of hierarchical levels can be defined. Eachhierarchical node can be assigned one or more technology diagrams 10,whose sections 24, 25 respectively correspond to function diagrams 27for the individual level. The function diagrams 27 in turn comprise oneor more modules 32. The function diagrams 27 and their modules 32 can beclearly assigned to a particular section 24, 25 of a technology diagram10 by means of their identification 31, 65. The section 24, 25 isclearly identified by means of the identification 37. This allows anassociation with the respective technology diagram 10, which is in turncharacterized by means of the identification 26.

For the technology diagrams 10, an identification 26 is preferably usedwhich extends over the whole installation 60. This allows clear links tobe made between different technology diagrams 10 which are notassociated with the same function identifier 62 or with the sameautomation system 61. These links can thus extend over the entireinstallation 60. FIG. 9 schematically shows a report. Linked reports areconfigured entirely in the technology diagram 10, since this is wherethe associated combinational logic is shown. The report itself isrepresented by a separate symbol 67 which is assigned precisely onereport module when the function diagrams 27 are generated. On the basisof the measurement result or the logic combination, an output 63 isgiven whose individual report attributes can be configured directly forthe technology diagram 10. In addition, configuration is provided inother fields. The associated diagram symbol 23 contains not only theidentification 26′ but also a name 64.

During the configuration of the reports, a distinction is made betweendifferent types. Reports filed on a standard basis, such as statusreports and failure reports, are elements of the instrumentation andcontrol system components. These reports are an element of theinstrumentation and control 12 and cannot be manipulated in thetechnology diagram. Fault reports arising in this context need to beable to be provided separately from the rest of the fault reports andspecifically. If failure reports relevant to factory management arise,the operator of the installation 60 needs to be notified of these,because he needs to react to restrictions of availability or torestrictions of load capability. The corresponding reports areconfigured in the technology diagram 10. This also applies to reportswhich concern failures of control and regulation functions. Theindividual reports are requests to the operator to perform particularactions. The respective actions to be performed are generally indicatedin the operating manual. Each report is therefore advantageouslyassigned a break point relating to the operating manual in order toallow fast access.

FIG. 10 schematically shows the transfer of information between atechnology diagram 10 and a function diagram 27. Each symbol 21 in thetechnology diagram 10 has various associated information, shownschematically by the sub-regions I, II. The information from thesub-region I is shown in a technology diagram 10, while the informationfrom the sub-region II is suppressed. This increases clarity. Thesub-region III is used for holding information which is not contained inthe technology diagram 10. This information relates to details of theinstrumentation and control which are not relevant to the basic conceptand are in may cases not yet known or have not been definitivelystipulated when producing the technology diagram 10. However, it ispossible to determine clearly which information is still required forgenerating the associated function diagram 27, so that memory space andbreak points 50 can be provided accordingly.

With the assignment of the symbol 21 to the module 32 of the respectivefunction diagram 27 by means of the identification 36, 65 as shown byarrow 66, the information is automatically transferred from thesub-region I, II to the function diagram 27. At the same time, anindication is given that information needs to be added to the sub-regionIII. This is done manually directly in the function diagram 27 or in thetechnology diagram 10 immediately before the generation. Following theaddition of this information, the assigned individual sequence 53 isautomatically generated. For the purpose of assignment, each individualsequence 53 is provided with an identification 68. To generate theindividual sequence 53, use is made of a plurality of modules 32, as isshown schematically by arrows 69.

FIG. 11 schematically shows another embodiment of the inventive method.The technology diagram 10 has two interfaces 72, 73 for importinginformation from other engineering systems 70, 71, as shown by arrow 74,75. The process engineering and the instrumentation and control areconfigured in these engineering systems 70, 71 in advance and are thenput together in the technology diagram 10. Engineering systems 70, 71which are known in this context can be used. Naturally, information canalso be exported from the technology diagram 10 into one or moreengineering systems, as indicated by the arrow 82.

When the information has been imported, the technology diagram 10 issubjected to a plausibility check 76. This plausibility check 6 isadvantageously also performed after changes to the technology diagram10. When configuration is complete, the function diagrams 27 areautomatically generated, as shown by the arrows 78. During generation, aconsistency check 77 is performed, for example using the defined breakpoints 50 and the respective identifications used. This consistencycheck 77 is also performed between the individual function diagrams 27.

If the technology diagram has gaps as per the sub-region III from FIG.10, these gaps are input manually using an interface 79, as shown byarrow 80. Alternatively, the information required for generating thefunction diagrams 27 completely can be retrieved from a library.

Once the function diagrams 27 have been completed, the respectivelyassigned individual sequences 53 are automatically produced and puttogether in the program code 52 for instrumentation and control.

An embodiment of the inventive method makes it possible to showprocess-engineering diagrams 11 and diagrams 12 for instrumentation andcontrol in a joint technology diagram 10. The technology diagram 10 canbe matched to changes made in other engineering systems 70, 71 quickly,easily and without errors by importing information. The cooperationbetween the process engineering operatives and the control operatives isfacilitated considerably, however. According to an embodiment of theinvention, once the technology diagram 10 has been produced, therequired function diagrams 27 for the individual level are generatedautomatically. Manual implementation and manual configuration of changeare no longer necessary, which means that errors arising to date whenproducing the function diagrams 27 are completely precluded. Detailedinformation which is not required for the cooperation between theprocess-engineering operatives and the control operatives can be addedto the technology diagram and/or to the automatically generated functiondiagrams 27 at a later time.

Besides the pure information for the diagrams 11, 12, other graphicalsymbols can be imported from the engineering systems 70, 71 or can beproduced independently. This allows individual matching to therespective operatives, which again improves clarity.

The invention being thus described, it will be obvious that the same maybe varied in many ways. Such variations are not to be regarded as adeparture from the spirit and scope of the invention, and all suchmodifications as would be obvious to one skilled in the art are intendedto be included within the scope of the following claims.

1. A method for automatically producing program code for instrumentationand control, for operating an installation with process-engineeringcomponents, where a machine-readable technology diagram for theinstallation is provided which contains both a graphical diagram of theprocess engineering and a further graphical diagram of the program code,the graphical diagram of the process engineering and the furthergraphical diagram of the program code being shown together in themachine readable technology diagram, and the further diagram beingdivided into a number of sections which each including one or moreinterlinked symbols which schematically represents the program code tobe produced, comprising: a) automatically assigning each symbol in asection a functional module, wherein links between symbols areautomatically used to stipulate links between functional modules so thata function diagram for the section of the further diagram is formablefrom the functional modules and respective links; b) automaticallyproducing, using each function diagram, a respective individual sequenceof the program code for each section; and c) automatically producing theprogram code from the produced individual sequences.
 2. The method asclaimed in claim 1, wherein producing the function diagrams involves acheck being carried out to determine whether the information requiredfor producing the function diagrams is contained in the technologydiagram.
 3. The method as claimed in claim 2, wherein precisely onefunction diagram is produced from precisely one section.
 4. The methodas claimed in claim 3, wherein each section includes a series ofsymbols, and each of these symbols is assigned to precisely one moduleof the associated function diagram.
 5. The method as claimed in claim 1,wherein precisely one individual sequence is generated from eachfunction diagram.
 6. The method as claimed in claim 2, wherein, toimprove clarity, at least one of a plurality of symbols and a pluralityof sections of the technology diagram are combined and put together toform a diagram symbol.
 7. The method as claimed in claim 1, whereinsymbols contained in the technology diagram are provided with anidentification.
 8. The method as claimed in claim 1, wherein thetechnology diagram is subjected to a validity check.
 9. The method asclaimed in claim 1, wherein a consistency check is carried out betweenthe individual function diagrams and between the function diagrams andthe technology diagram.
 10. The method as claimed in claim 1, whereinthe technology diagram is provided with at least one interface forconnecting it to other engineering systems.
 11. The method as claimed inclaim 10, wherein information is imported into the technology diagramfrom other engineering systems.
 12. The method as claimed in claim 10,wherein information is exported from the technology diagram to otherengineering systems.
 13. The method as claimed in claim 1, whereininformation contained in the technology diagram is shown graphically.14. The method as claimed in claim 13, wherein, to show the information,graphical symbols are imported into the technology diagram.
 15. Themethod as claimed in claim 13, wherein a portion of the informationcontained in the technology diagram is shown graphically.
 16. The methodas claimed in claim 1, wherein a portion of the information required forfully generating the function diagrams and individual sequences isincluded in the technology diagram.
 17. The method as claimed in claim16, wherein generation of the function diagrams involves theidentification and display of gaps in the information contained in thetechnology diagram.
 18. The method as claimed in claim 11, whereininformation is exported from the technology diagram to other engineeringsystems.
 19. The method as claimed in claim 14, wherein a portion of theinformation contained in the technology diagram is shown graphically.20. The method as claimed in claim 1, wherein each function diagramcorresponds to at least one software module.
 21. The method of claim 1,wherein each function diagram corresponds to a process engineeringfunction.
 22. A method for automatically producing program code for usein an installation with process-engineering components, comprising:providing a machine-readable technology diagram for the installation,the diagram being divided into a number of sections, each including oneor more symbols; assigning each symbol in a section a functional module,wherein links between symbols stipulate links between functionalmodules, and wherein a functional diagram is automatically generateablefor each section from corresponding symbols and links; and assigningprogram code to functional modules, wherein a respective individualsequence of the program code is automatically generateable from afunctional diagram and wherein the program code is automaticallyproduceable from the individual sequences; wherein the machine-readabletechnology diagram shows a graphical diagram of the process-engineeringcomponents and a graphical diagram of the program code concurrently. 23.The method as claimed in claim 22, wherein precisely one functiondiagram is produced from precisely one section.
 24. The method asclaimed in claim 23, wherein each section includes a series of symbols,and each of these symbols is assigned to precisely one module of theassociated function diagram.
 25. The method as claimed in claim 22,wherein precisely one individual sequence is generated from eachfunction diagram.
 26. The method as claimed in claim 22, whereininformation is imported into the technology diagram from otherengineering systems.
 27. The method as claimed in claim 22, whereininformation is exported from the technology diagram to other engineeringsystems.
 28. The method as claimed in claim 22, wherein informationcontained in the technology diagram is shown graphically.
 29. The methodas claimed in claim 28, wherein, to show the information, graphicalsymbols are imported into the technology diagram.